Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1261ca636d2a217c7dd05f175f8caf87e4f88e9f5527a80795ca55373b99738f

Tx prefix hash: bd3747980607e3e61ed24707257cb4decb5af71ef0f60814b3c2a08a8d02f9d5
Tx public key: 30a555604cc508fec06d134b07ad5e5ad399d03ef16550e192e2d4ef8cb06313
Timestamp: 1672743295 Timestamp [UCT]: 2023-01-03 10:54:55 Age [y:d:h:m:s]: 02:158:20:38:34
Block: 666636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635273 RingCT/type: yes/0
Extra: 0130a555604cc508fec06d134b07ad5e5ad399d03ef16550e192e2d4ef8cb0631302110000000552542ceb000000000000000000

1 output(s) for total of 3.794531482000 dcy

stealth address amount amount idx
00: 46ff2e46a238c11d0e2ecb8c2399ef8c3f33f1a94f5102ce8b09c4d7444e50ec 3.794531482000 1107765 of 0

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": 666646, "vin": [ { "gen": { "height": 666636 } } ], "vout": [ { "amount": 3794531482, "target": { "key": "46ff2e46a238c11d0e2ecb8c2399ef8c3f33f1a94f5102ce8b09c4d7444e50ec" } } ], "extra": [ 1, 48, 165, 85, 96, 76, 197, 8, 254, 192, 109, 19, 75, 7, 173, 94, 90, 211, 153, 208, 62, 241, 101, 80, 225, 146, 226, 212, 239, 140, 176, 99, 19, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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