Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c68947182a9288bba7d6da762d30b7eb8b384fa09d128421a1baabcc501dc4

Tx prefix hash: c67a0bc3d3c894ffd519d125ab260e920e6adc81871f038c9e15c5ef5f812e5a
Tx public key: ed53d265d3bc2be92321d1df0716296b2e2238b80ef432cf2dc88a04276fc415
Timestamp: 1727022412 Timestamp [UCT]: 2024-09-22 16:26:52 Age [y:d:h:m:s]: 00:111:02:28:22
Block: 1115777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79437 RingCT/type: yes/0
Extra: 01ed53d265d3bc2be92321d1df0716296b2e2238b80ef432cf2dc88a04276fc41502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d66715627f9421b6f44014b6e5399c04b3db9ba9dd929b1c42d80630de8b4491 0.600000000000 1596026 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": 1115787, "vin": [ { "gen": { "height": 1115777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d66715627f9421b6f44014b6e5399c04b3db9ba9dd929b1c42d80630de8b4491" } } ], "extra": [ 1, 237, 83, 210, 101, 211, 188, 43, 233, 35, 33, 209, 223, 7, 22, 41, 107, 46, 34, 56, 184, 14, 244, 50, 207, 45, 200, 138, 4, 39, 111, 196, 21, 2, 17, 0, 0, 0, 7, 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