Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bc62ed452e46af8e4016f364fff0506fcf7f3d3a4df3b8d48a1a00f6434e7bcf

Tx prefix hash: 3805cf5c9991638268a4d29368664dc20177f3646279b82838e8f5fc2d5860cc
Tx public key: aa7e3021e566946e1ed3dec8b3fd6e1e69f41d4d53f2c77ff7f8d7cc6d7582c6
Timestamp: 1737463752 Timestamp [UCT]: 2025-01-21 12:49:12 Age [y:d:h:m:s]: 00:150:07:28:40
Block: 1202151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107120 RingCT/type: yes/0
Extra: 01aa7e3021e566946e1ed3dec8b3fd6e1e69f41d4d53f2c77ff7f8d7cc6d7582c60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300f3de496b4be53d9ddb177b7cecee1a117f4d9b77ec42387570966330ded11 0.600000000000 1688812 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1202161, "vin": [ { "gen": { "height": 1202151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300f3de496b4be53d9ddb177b7cecee1a117f4d9b77ec42387570966330ded11" } } ], "extra": [ 1, 170, 126, 48, 33, 229, 102, 148, 110, 30, 211, 222, 200, 179, 253, 110, 30, 105, 244, 29, 77, 83, 242, 199, 127, 247, 248, 215, 204, 109, 117, 130, 198, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8