Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96cd57ef74bcbbd85d406dd9c07f799775ca7492fa1dff6a8c4b6fcf2bb917d0

Tx prefix hash: 6446b0d62e9d05ab57bca38da9b526941147579912de214fd2f674b5459b58f2
Tx public key: 71ce8250a81c714a71c9e9e443bf5cf911d88d30a76af8c2d97c86c03f1889a2
Timestamp: 1729633938 Timestamp [UCT]: 2024-10-22 21:52:18 Age [y:d:h:m:s]: 00:216:20:20:08
Block: 1137387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154825 RingCT/type: yes/0
Extra: 0171ce8250a81c714a71c9e9e443bf5cf911d88d30a76af8c2d97c86c03f1889a20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78a6d890313dfbcde05562e4ed6c6ce957536b4627dbd59e0134909d60115e98 0.600000000000 1620868 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": 1137397, "vin": [ { "gen": { "height": 1137387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78a6d890313dfbcde05562e4ed6c6ce957536b4627dbd59e0134909d60115e98" } } ], "extra": [ 1, 113, 206, 130, 80, 168, 28, 113, 74, 113, 201, 233, 228, 67, 191, 92, 249, 17, 216, 141, 48, 167, 106, 248, 194, 217, 124, 134, 192, 63, 24, 137, 162, 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