Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaf80657724c09b9f1fad3f93cfe6428c9abfbdc8da60ca603ab020ebf9d5444

Tx prefix hash: 362edf30202580e17c43351eba15ef743256f30b1de181b7bbd0b4c27146163a
Tx public key: 3d33266e8754cd382fa1a4e245366e4c1d79c9a38321928b9e822d3744bf0b12
Timestamp: 1723720417 Timestamp [UCT]: 2024-08-15 11:13:37 Age [y:d:h:m:s]: 00:233:02:57:08
Block: 1088401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166483 RingCT/type: yes/0
Extra: 013d33266e8754cd382fa1a4e245366e4c1d79c9a38321928b9e822d3744bf0b1202110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f4a8d6ad5deb3bb1af9855acde7504aa85cfb684929186e42e3490dc7d37d4d 0.600000000000 1563016 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": 1088411, "vin": [ { "gen": { "height": 1088401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f4a8d6ad5deb3bb1af9855acde7504aa85cfb684929186e42e3490dc7d37d4d" } } ], "extra": [ 1, 61, 51, 38, 110, 135, 84, 205, 56, 47, 161, 164, 226, 69, 54, 110, 76, 29, 121, 201, 163, 131, 33, 146, 139, 158, 130, 45, 55, 68, 191, 11, 18, 2, 17, 0, 0, 0, 11, 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