Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a6c3170c00606f1911115fbb037ea4a74c2230baff24e1cc20b5827153d4d43

Tx prefix hash: 0518f5a0b36923a3fd04485c98e300fd2a2b54e36e81f61555949a0500e1bb1b
Tx public key: 0cf3d20181341bd4729742b77fd250a8a1234bafb962d8daca8a19ec7b2ac378
Timestamp: 1582433251 Timestamp [UCT]: 2020-02-23 04:47:31 Age [y:d:h:m:s]: 04:281:10:50:45
Block: 70553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093804 RingCT/type: yes/0
Extra: 010cf3d20181341bd4729742b77fd250a8a1234bafb962d8daca8a19ec7b2ac378021100000001724f989b000000000000000000

1 output(s) for total of 358.285659656000 dcy

stealth address amount amount idx
00: 07ca2dae2f764d0c9ea4f6db8dbf89da4bd63109dd22e595c871afcdfa89da2c 358.285659656000 130391 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": 70563, "vin": [ { "gen": { "height": 70553 } } ], "vout": [ { "amount": 358285659656, "target": { "key": "07ca2dae2f764d0c9ea4f6db8dbf89da4bd63109dd22e595c871afcdfa89da2c" } } ], "extra": [ 1, 12, 243, 210, 1, 129, 52, 27, 212, 114, 151, 66, 183, 127, 210, 80, 168, 161, 35, 75, 175, 185, 98, 216, 218, 202, 138, 25, 236, 123, 42, 195, 120, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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