Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96eabb382268fe06a48d69f923bd3388aee0149fbcc7df4cf48a1442b02eebaa

Tx prefix hash: 4960c0da803dc253d12174b426b7d81ef6c367871d66b813fe9b1579db6ce018
Tx public key: 91c01b2c0c77bd1adf3c2b1f491e1f59d2ec2541eff889976f1bb3fe9aae0f9b
Timestamp: 1657811766 Timestamp [UCT]: 2022-07-14 15:16:06 Age [y:d:h:m:s]: 02:168:03:08:41
Block: 543652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641530 RingCT/type: yes/0
Extra: 0191c01b2c0c77bd1adf3c2b1f491e1f59d2ec2541eff889976f1bb3fe9aae0f9b02110000000475e3f0e9000000000000000000

1 output(s) for total of 9.697401676000 dcy

stealth address amount amount idx
00: 80a47f620c829dcceabbfea525dc82b0fb47fbb38a336a017a12ea052d1ea230 9.697401676000 974343 of 0

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": 543662, "vin": [ { "gen": { "height": 543652 } } ], "vout": [ { "amount": 9697401676, "target": { "key": "80a47f620c829dcceabbfea525dc82b0fb47fbb38a336a017a12ea052d1ea230" } } ], "extra": [ 1, 145, 192, 27, 44, 12, 119, 189, 26, 223, 60, 43, 31, 73, 30, 31, 89, 210, 236, 37, 65, 239, 248, 137, 151, 111, 27, 179, 254, 154, 174, 15, 155, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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