Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e58c2369bab77d04e4b582f1001c2898438fbc7e5fa916e9327aa9beaab7986

Tx prefix hash: 0e2592cb7f9788c7e2c267c61169d23ef892976bcffaea290d038125c6d5d735
Tx public key: 17a18d40425e04cb91ea74be26f690a4e2be448b86a7ad3b57de1e13036dd1dc
Timestamp: 1746409921 Timestamp [UCT]: 2025-05-05 01:52:01 Age [y:d:h:m:s]: 00:200:13:11:25
Block: 1275973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141047 RingCT/type: yes/0
Extra: 0117a18d40425e04cb91ea74be26f690a4e2be448b86a7ad3b57de1e13036dd1dc0211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08ccb97774b766bbd7d826b48c1d1e2fccadd1a6dc867d27738ebc761bad6391 0.600000000000 1763288 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": 1275983, "vin": [ { "gen": { "height": 1275973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08ccb97774b766bbd7d826b48c1d1e2fccadd1a6dc867d27738ebc761bad6391" } } ], "extra": [ 1, 23, 161, 141, 64, 66, 94, 4, 203, 145, 234, 116, 190, 38, 246, 144, 164, 226, 190, 68, 139, 134, 167, 173, 59, 87, 222, 30, 19, 3, 109, 209, 220, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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