Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e158e6debac0b6b632a4ca015da290bf998d037e2c541fc43fcde8eb78001533

Tx prefix hash: 276c6fd254ab88e00d2209f27474d6cda1bb15417dfa24be2cda57e8e6157f02
Tx public key: dd3a2bc9f6ef29b3d195c5fa67510508ff968e6f72ab22c9739e2f5235f2d27c
Timestamp: 1735642500 Timestamp [UCT]: 2024-12-31 10:55:00 Age [y:d:h:m:s]: 00:098:02:42:50
Block: 1187110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69901 RingCT/type: yes/0
Extra: 01dd3a2bc9f6ef29b3d195c5fa67510508ff968e6f72ab22c9739e2f5235f2d27c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74657aeef764988ddfdc821772f4e8fa403ec1dac9eb170f6b8f7df0ebe0f17f 0.600000000000 1673597 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": 1187120, "vin": [ { "gen": { "height": 1187110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74657aeef764988ddfdc821772f4e8fa403ec1dac9eb170f6b8f7df0ebe0f17f" } } ], "extra": [ 1, 221, 58, 43, 201, 246, 239, 41, 179, 209, 149, 197, 250, 103, 81, 5, 8, 255, 150, 142, 111, 114, 171, 34, 201, 115, 158, 47, 82, 53, 242, 210, 124, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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