Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2bcd648a2622ac91c20045e0802b41549a0b475cb713d91081913b6e72bc62

Tx prefix hash: ec42c4a19bfee248d3be84a84f19addd26aa1ade76d47a4498401ac74d7b4e1a
Tx public key: 31e2c29691753864cfe73bc974f449a212d047b0fe4ec5746a5d3daa9c330d63
Timestamp: 1709660877 Timestamp [UCT]: 2024-03-05 17:47:57 Age [y:d:h:m:s]: 01:254:07:08:46
Block: 971842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440475 RingCT/type: yes/0
Extra: 0131e2c29691753864cfe73bc974f449a212d047b0fe4ec5746a5d3daa9c330d6302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48fb76a05b3b9ebd88d2247ebd8b56b0989471ddeb61f60243d178b341854a17 0.600000000000 1431745 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": 971852, "vin": [ { "gen": { "height": 971842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48fb76a05b3b9ebd88d2247ebd8b56b0989471ddeb61f60243d178b341854a17" } } ], "extra": [ 1, 49, 226, 194, 150, 145, 117, 56, 100, 207, 231, 59, 201, 116, 244, 73, 162, 18, 208, 71, 176, 254, 78, 197, 116, 106, 93, 61, 170, 156, 51, 13, 99, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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