Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0be6bd83ff5f02a46af0f6aae2597138a1f29c4304a82b4b92c85f4d898c20

Tx prefix hash: 3cc4d88df990de31cd5d245ddd74d6ca74b4fe37771116eeded4f55b76224d0c
Tx public key: 7a308fce5018fb8fae5b008df1d13cb04ee273fb392a76db70d68d0cf7375f4f
Timestamp: 1698392662 Timestamp [UCT]: 2023-10-27 07:44:22 Age [y:d:h:m:s]: 01:151:05:25:58
Block: 878637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369061 RingCT/type: yes/0
Extra: 017a308fce5018fb8fae5b008df1d13cb04ee273fb392a76db70d68d0cf7375f4f02110000000433af99f4000000000000000000

1 output(s) for total of 0.752854229000 dcy

stealth address amount amount idx
00: 1595edd5d6245fd0018c9d4dbee272587315b3e24bc41aa99cc23c75fa47e3f2 0.752854229000 1334099 of 0

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": 878647, "vin": [ { "gen": { "height": 878637 } } ], "vout": [ { "amount": 752854229, "target": { "key": "1595edd5d6245fd0018c9d4dbee272587315b3e24bc41aa99cc23c75fa47e3f2" } } ], "extra": [ 1, 122, 48, 143, 206, 80, 24, 251, 143, 174, 91, 0, 141, 241, 209, 60, 176, 78, 226, 115, 251, 57, 42, 118, 219, 112, 214, 141, 12, 247, 55, 95, 79, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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