Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acbb2aa06608061b91c2821c01cccd7998309e6ff1ad2092fec1e19283935ead

Tx prefix hash: eb86e0a779b989f8ea1a05b467ac560f2690b8fd2871d80f30d5b26c4acfa8b3
Tx public key: 61538690038eb9360860466bd69fda25b57773e6cb8aa659a744e7cab38a2a0a
Timestamp: 1727298166 Timestamp [UCT]: 2024-09-25 21:02:46 Age [y:d:h:m:s]: 00:181:16:39:06
Block: 1118064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129652 RingCT/type: yes/0
Extra: 0161538690038eb9360860466bd69fda25b57773e6cb8aa659a744e7cab38a2a0a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c4d9c93362c0ae0d9eb9e15ee1fdb0d856f0246c3f0e85c34d8bfbb35a646a9 0.600000000000 1599127 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": 1118074, "vin": [ { "gen": { "height": 1118064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c4d9c93362c0ae0d9eb9e15ee1fdb0d856f0246c3f0e85c34d8bfbb35a646a9" } } ], "extra": [ 1, 97, 83, 134, 144, 3, 142, 185, 54, 8, 96, 70, 107, 214, 159, 218, 37, 181, 119, 115, 230, 203, 138, 166, 89, 167, 68, 231, 202, 179, 138, 42, 10, 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