Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5545a0e77dd67150d75303862bbb999b355f61006e3a68622d7b0a4696498e4

Tx prefix hash: b9fdb1725f939004cf8faab97149f7003128475cfb9d60a0f58b6ca9fff5e48c
Tx public key: c5485832218adefde5da5749c0c9e81962b559fbd7e5dc0052ce70db1b42f4e5
Timestamp: 1721982502 Timestamp [UCT]: 2024-07-26 08:28:22 Age [y:d:h:m:s]: 00:245:05:45:20
Block: 1073988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175183 RingCT/type: yes/0
Extra: 01c5485832218adefde5da5749c0c9e81962b559fbd7e5dc0052ce70db1b42f4e502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 604262a77b4c93f0e5d7c497652b4e89d67dc95c6364bd7b2f78ac697f88a339 0.600000000000 1546497 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": 1073998, "vin": [ { "gen": { "height": 1073988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "604262a77b4c93f0e5d7c497652b4e89d67dc95c6364bd7b2f78ac697f88a339" } } ], "extra": [ 1, 197, 72, 88, 50, 33, 138, 222, 253, 229, 218, 87, 73, 192, 201, 232, 25, 98, 181, 89, 251, 215, 229, 220, 0, 82, 206, 112, 219, 27, 66, 244, 229, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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