Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091cf5f5eb9b4fb5755aa5ad45665fa395237daa3dcf65aac9bc71a0651d68c9

Tx prefix hash: 6c32a1ce9c996c65a20cf4ca3e82c1af007e81a3d1311086d4d4efdf61022b3e
Tx public key: f2a6014912e751b6eef96ba1069ffec08b821f537d0d42217065a1dee5475a6e
Timestamp: 1728259717 Timestamp [UCT]: 2024-10-07 00:08:37 Age [y:d:h:m:s]: 00:204:17:22:08
Block: 1126034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146130 RingCT/type: yes/0
Extra: 01f2a6014912e751b6eef96ba1069ffec08b821f537d0d42217065a1dee5475a6e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6006ccfa71eeb3999bd3b1ce700449e4afbc775d5b57f987a28c89e55bb0a47e 0.600000000000 1608807 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": 1126044, "vin": [ { "gen": { "height": 1126034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6006ccfa71eeb3999bd3b1ce700449e4afbc775d5b57f987a28c89e55bb0a47e" } } ], "extra": [ 1, 242, 166, 1, 73, 18, 231, 81, 182, 238, 249, 107, 161, 6, 159, 254, 192, 139, 130, 31, 83, 125, 13, 66, 33, 112, 101, 161, 222, 229, 71, 90, 110, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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