Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9acda7c2e335c83cb25211a55cf25e92bcd6f9712616c1bff3ebc8ac20fc82d1

Tx prefix hash: 19c43907f7c4b93326ff4b249bab8fe6db44b69dc9949fe2a1095b3aad9fb97b
Tx public key: 14b1e8e9e4304141396196cbcba0d94496e44a7a2a6272062c9237dfa7ab6dc2
Timestamp: 1728659108 Timestamp [UCT]: 2024-10-11 15:05:08 Age [y:d:h:m:s]: 00:176:19:33:47
Block: 1129345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126158 RingCT/type: yes/0
Extra: 0114b1e8e9e4304141396196cbcba0d94496e44a7a2a6272062c9237dfa7ab6dc2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02ec21610e0909aab8155d2c011af407c274e3937387b6030f2db92564df7368 0.600000000000 1612170 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": 1129355, "vin": [ { "gen": { "height": 1129345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02ec21610e0909aab8155d2c011af407c274e3937387b6030f2db92564df7368" } } ], "extra": [ 1, 20, 177, 232, 233, 228, 48, 65, 65, 57, 97, 150, 203, 203, 160, 217, 68, 150, 228, 74, 122, 42, 98, 114, 6, 44, 146, 55, 223, 167, 171, 109, 194, 2, 17, 0, 0, 0, 6, 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