Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299122c70282935a63aaebae8cbc19dc0963e9cb4022c9b3b7ba82fb885e5ccf

Tx prefix hash: e2f8d5fe09c6b09e7088ae937cac9f028e395dbc0d919067e52fbe29feb18c1f
Tx public key: f38d007540c09017866300117159f8b116a66a220e32118bc5aff2e329de3d2e
Timestamp: 1717795473 Timestamp [UCT]: 2024-06-07 21:24:33 Age [y:d:h:m:s]: 00:282:02:12:26
Block: 1039282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201602 RingCT/type: yes/0
Extra: 01f38d007540c09017866300117159f8b116a66a220e32118bc5aff2e329de3d2e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b873ecfd8df8e7e8ee2a7d57cb95773d1cc7ffd414ababa0ddc14238076d177 0.600000000000 1507915 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": 1039292, "vin": [ { "gen": { "height": 1039282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b873ecfd8df8e7e8ee2a7d57cb95773d1cc7ffd414ababa0ddc14238076d177" } } ], "extra": [ 1, 243, 141, 0, 117, 64, 192, 144, 23, 134, 99, 0, 17, 113, 89, 248, 177, 22, 166, 106, 34, 14, 50, 17, 139, 197, 175, 242, 227, 41, 222, 61, 46, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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