Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49246fb0f60e304ed8503320610fce451b2050dc40ec811e2740d3e21fd2fe8e

Tx prefix hash: 784b394a6c1f6742f5fb35ca9f92714bc45cd89907d45e7893eb172cbdddf8ba
Tx public key: a7346e4a6dd1a59836cdb0f6728b23fc2ace60df26327e3f22faa57c07c7fbee
Timestamp: 1728081833 Timestamp [UCT]: 2024-10-04 22:43:53 Age [y:d:h:m:s]: 00:253:12:35:09
Block: 1124557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180942 RingCT/type: yes/0
Extra: 01a7346e4a6dd1a59836cdb0f6728b23fc2ace60df26327e3f22faa57c07c7fbee021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4fffc84c0a37910ab254cfd96ec75b7cebff1a473a6324123b6c85e5b485382 0.600000000000 1607198 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": 1124567, "vin": [ { "gen": { "height": 1124557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4fffc84c0a37910ab254cfd96ec75b7cebff1a473a6324123b6c85e5b485382" } } ], "extra": [ 1, 167, 52, 110, 74, 109, 209, 165, 152, 54, 205, 176, 246, 114, 139, 35, 252, 42, 206, 96, 223, 38, 50, 126, 63, 34, 250, 165, 124, 7, 199, 251, 238, 2, 17, 0, 0, 0, 5, 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