Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab954082559bc60c474e2fde0b1f12f2c67e93fa7f50f640f2c73efce925c6dc

Tx prefix hash: 3e05f951879868dc50b42eee08eaea576f161ac2b7f89eb785e32ce04f1cfb86
Tx public key: 8ed2808e1e37cabc9a19a30f9da057ca7448753e0cb3384fbfdef90b811125bc
Timestamp: 1703022925 Timestamp [UCT]: 2023-12-19 21:55:25 Age [y:d:h:m:s]: 01:111:13:54:07
Block: 916812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340876 RingCT/type: yes/0
Extra: 018ed2808e1e37cabc9a19a30f9da057ca7448753e0cb3384fbfdef90b811125bc021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17b0e98ec358573c980b8a6a2fdba685f9d1ae40a386a14ba9c95f27ab05f001 0.600000000000 1374372 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": 916822, "vin": [ { "gen": { "height": 916812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17b0e98ec358573c980b8a6a2fdba685f9d1ae40a386a14ba9c95f27ab05f001" } } ], "extra": [ 1, 142, 210, 128, 142, 30, 55, 202, 188, 154, 25, 163, 15, 157, 160, 87, 202, 116, 72, 117, 62, 12, 179, 56, 79, 191, 222, 249, 11, 129, 17, 37, 188, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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