Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38eefdd8f7cf07cb6e8ca5bd2030aa72ca6cf952d9dc9d3ff8c6d67ec8db4562

Tx prefix hash: 9e366f6a29bc218adb6aed2613db2d6023a6ebd438a05ebc3410874d41f265e8
Tx public key: b9084eecd35a775c88a17b3c0a393218bd10534cc06ef527364336564a73a313
Timestamp: 1728327501 Timestamp [UCT]: 2024-10-07 18:58:21 Age [y:d:h:m:s]: 00:047:11:47:37
Block: 1126591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33921 RingCT/type: yes/0
Extra: 01b9084eecd35a775c88a17b3c0a393218bd10534cc06ef527364336564a73a313021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fef503b4c418f4f7e1618f61c061699884dbd0e1645ea407ada9273ae1519571 0.600000000000 1609386 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": 1126601, "vin": [ { "gen": { "height": 1126591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fef503b4c418f4f7e1618f61c061699884dbd0e1645ea407ada9273ae1519571" } } ], "extra": [ 1, 185, 8, 78, 236, 211, 90, 119, 92, 136, 161, 123, 60, 10, 57, 50, 24, 189, 16, 83, 76, 192, 110, 245, 39, 54, 67, 54, 86, 74, 115, 163, 19, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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