Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 422202a25b6cb043088ca841277046e4d1e898fca8f953323dfcc3263142deae

Tx prefix hash: 17e3b827083582121ee3e5c47a7281e104019ea3e3b80a9216bdcaae3543c1b6
Tx public key: 3bb0deb686729f423345e1331df137e7c5310555e85aa399fb0aa17e7b6288cf
Timestamp: 1718969648 Timestamp [UCT]: 2024-06-21 11:34:08 Age [y:d:h:m:s]: 00:273:23:20:30
Block: 1048992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195791 RingCT/type: yes/0
Extra: 013bb0deb686729f423345e1331df137e7c5310555e85aa399fb0aa17e7b6288cf02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1344b6cf5932a3c0106a649498b991b425501ca70e91fccfab5b2d80d339d9b0 0.600000000000 1519089 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": 1049002, "vin": [ { "gen": { "height": 1048992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1344b6cf5932a3c0106a649498b991b425501ca70e91fccfab5b2d80d339d9b0" } } ], "extra": [ 1, 59, 176, 222, 182, 134, 114, 159, 66, 51, 69, 225, 51, 29, 241, 55, 231, 197, 49, 5, 85, 232, 90, 163, 153, 251, 10, 161, 126, 123, 98, 136, 207, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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