Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67b19b54e266f395e0f7f11873ff5b7018cc9ee47cebc8d1d1f52d7a2bf58af3

Tx prefix hash: d66a42181cafe498f479f910764ab7a100ff89d7af925c338d54281a83fbff4d
Tx public key: 7f49a77e30f1def37e60df3c541a42378188dde2b22089ad0e900ccd5b753ce8
Timestamp: 1733002985 Timestamp [UCT]: 2024-11-30 21:43:05 Age [y:d:h:m:s]: 00:106:02:55:49
Block: 1165258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75656 RingCT/type: yes/0
Extra: 017f49a77e30f1def37e60df3c541a42378188dde2b22089ad0e900ccd5b753ce80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6236c9ea9adf2f7d03c5bc9cfe2dd8a26ddbee35240e3d0d2e53f3345008fe93 0.600000000000 1650933 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": 1165268, "vin": [ { "gen": { "height": 1165258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6236c9ea9adf2f7d03c5bc9cfe2dd8a26ddbee35240e3d0d2e53f3345008fe93" } } ], "extra": [ 1, 127, 73, 167, 126, 48, 241, 222, 243, 126, 96, 223, 60, 84, 26, 66, 55, 129, 136, 221, 226, 178, 32, 137, 173, 14, 144, 12, 205, 91, 117, 60, 232, 2, 17, 0, 0, 0, 2, 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