Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 144f91c710653cb52ea2b76766be7f250bff6a53313c1137f0226854b43f026f

Tx prefix hash: fcd532251db7fefc183d376935200e9759f2d2781d621f5e32e86efb537d0440
Tx public key: 55de510ee67a2aed6c8e138535a88a8c49dd08ca9dcb2da1f240d7eafa9fefb5
Timestamp: 1712703843 Timestamp [UCT]: 2024-04-09 23:04:03 Age [y:d:h:m:s]: 01:008:15:38:35
Block: 997048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267161 RingCT/type: yes/0
Extra: 0155de510ee67a2aed6c8e138535a88a8c49dd08ca9dcb2da1f240d7eafa9fefb502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 301edfedd1dcd34bcdf8f6607fa19b72ac6f695fdc5a7183a97babce022273ec 0.600000000000 1457476 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": 997058, "vin": [ { "gen": { "height": 997048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "301edfedd1dcd34bcdf8f6607fa19b72ac6f695fdc5a7183a97babce022273ec" } } ], "extra": [ 1, 85, 222, 81, 14, 230, 122, 42, 237, 108, 142, 19, 133, 53, 168, 138, 140, 73, 221, 8, 202, 157, 203, 45, 161, 242, 64, 215, 234, 250, 159, 239, 181, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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