Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891c70f8e1efd5f92b87da5dd77aea81ca4423c62ad4adaea978cb1e703fe893

Tx prefix hash: 0ada4ed49e0304e4edbf3a3d66781bc863c9a6ea4f1e3ac68e4a32d010fc0ba6
Tx public key: c1ec0db7dd48be97ea34e47fc07549d670a6c52b3dc891db086680e144f14e43
Timestamp: 1762057769 Timestamp [UCT]: 2025-11-02 04:29:29 Age [y:d:h:m:s]: 00:006:06:52:55
Block: 1403120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4488 RingCT/type: yes/0
Extra: 01c1ec0db7dd48be97ea34e47fc07549d670a6c52b3dc891db086680e144f14e43021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaa2fa67e05a394108e59de1c3ed3f0c7ebd75158458c55ebc065239fa60168f 0.600000000000 1891447 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": 1403130, "vin": [ { "gen": { "height": 1403120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaa2fa67e05a394108e59de1c3ed3f0c7ebd75158458c55ebc065239fa60168f" } } ], "extra": [ 1, 193, 236, 13, 183, 221, 72, 190, 151, 234, 52, 228, 127, 192, 117, 73, 214, 112, 166, 197, 43, 61, 200, 145, 219, 8, 102, 128, 225, 68, 241, 78, 67, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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