Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da108421112973f5556a1706183f646a320ef7c7f7265e396e8b61ab5f1bc28

Tx prefix hash: c8563aee73e8e0e916113d37833f2be3e6ba580c78756ca220af347fa9d4271e
Tx public key: efb00aa3ba2382e1e3d30a5c1127e2b15b292a9ed4f649a90085b82fdf442a66
Timestamp: 1705334586 Timestamp [UCT]: 2024-01-15 16:03:06 Age [y:d:h:m:s]: 01:296:02:45:49
Block: 935956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470438 RingCT/type: yes/0
Extra: 01efb00aa3ba2382e1e3d30a5c1127e2b15b292a9ed4f649a90085b82fdf442a660211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e57fb4fc296d663f48d672e118763a9c7368a265fd2e47a9f116be9b4fa108a 0.600000000000 1393978 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": 935966, "vin": [ { "gen": { "height": 935956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e57fb4fc296d663f48d672e118763a9c7368a265fd2e47a9f116be9b4fa108a" } } ], "extra": [ 1, 239, 176, 10, 163, 186, 35, 130, 225, 227, 211, 10, 92, 17, 39, 226, 177, 91, 41, 42, 158, 212, 246, 73, 169, 0, 133, 184, 47, 223, 68, 42, 102, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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