Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec2297639f8ad10948604bd03d12c6d73c6fcea343798c45e70c44f0e96c931

Tx prefix hash: 05463035e40238ad8e1e8acebd6b0c4d40db493022ea8027c88b1e5e4028249a
Tx public key: a5d60fa9bc086d8fd0e57e326e3149139455e543865ff3c156e7fa440c0b82d3
Timestamp: 1705634378 Timestamp [UCT]: 2024-01-19 03:19:38 Age [y:d:h:m:s]: 01:154:21:55:33
Block: 938429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371693 RingCT/type: yes/0
Extra: 01a5d60fa9bc086d8fd0e57e326e3149139455e543865ff3c156e7fa440c0b82d302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79cb4ea5502b3321a0d64a3cba64a95148870aff16ed7964d75aa14b22daf01e 0.600000000000 1396499 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": 938439, "vin": [ { "gen": { "height": 938429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79cb4ea5502b3321a0d64a3cba64a95148870aff16ed7964d75aa14b22daf01e" } } ], "extra": [ 1, 165, 214, 15, 169, 188, 8, 109, 143, 208, 229, 126, 50, 110, 49, 73, 19, 148, 85, 229, 67, 134, 95, 243, 193, 86, 231, 250, 68, 12, 11, 130, 211, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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