Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4441c8a4ca346bb4be85a3828fdadf7afad5e31929969ba37833a145836138b1

Tx prefix hash: cc5f3f659c44eeb6f5a63235460e9af19ac6d40d54bdfe83bbf72d5829efb0d4
Tx public key: fe899f25f4ccd926f47bf59f5982d077f28f5aadcc4a6687690f623cff78576c
Timestamp: 1737580830 Timestamp [UCT]: 2025-01-22 21:20:30 Age [y:d:h:m:s]: 00:146:00:29:06
Block: 1203114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104097 RingCT/type: yes/0
Extra: 01fe899f25f4ccd926f47bf59f5982d077f28f5aadcc4a6687690f623cff78576c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e6992c3c9df581a2922eef595c1bf4fe27b9c1c502ebd5c72ee1149dd37ab4f 0.600000000000 1689787 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": 1203124, "vin": [ { "gen": { "height": 1203114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e6992c3c9df581a2922eef595c1bf4fe27b9c1c502ebd5c72ee1149dd37ab4f" } } ], "extra": [ 1, 254, 137, 159, 37, 244, 204, 217, 38, 244, 123, 245, 159, 89, 130, 208, 119, 242, 143, 90, 173, 204, 74, 102, 135, 105, 15, 98, 60, 255, 120, 87, 108, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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