Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be953aa30f6bad4f54192d535482e2b1e1d39ca69cb519ea6c22163efd60043e

Tx prefix hash: cf4f9da1e4bcaff4c891e5f244d863aab46a0525b0c0ddc96013f3e87f956825
Tx public key: 773c24c05e482d39fe16bef90bbe41dc9dcf983acd31d0fdb1319fd9545f6a97
Timestamp: 1582969000 Timestamp [UCT]: 2020-02-29 09:36:40 Age [y:d:h:m:s]: 04:265:03:02:19
Block: 73873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083244 RingCT/type: yes/0
Extra: 01773c24c05e482d39fe16bef90bbe41dc9dcf983acd31d0fdb1319fd9545f6a970211000000d056c366d3000000000000000000

1 output(s) for total of 349.324369435000 dcy

stealth address amount amount idx
00: ecdf1005e2557f9f545657fb997b029852300f2ff1bbd3d5e5784535a32b2ddd 349.324369435000 136509 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": 73883, "vin": [ { "gen": { "height": 73873 } } ], "vout": [ { "amount": 349324369435, "target": { "key": "ecdf1005e2557f9f545657fb997b029852300f2ff1bbd3d5e5784535a32b2ddd" } } ], "extra": [ 1, 119, 60, 36, 192, 94, 72, 45, 57, 254, 22, 190, 249, 11, 190, 65, 220, 157, 207, 152, 58, 205, 49, 208, 253, 177, 49, 159, 217, 84, 95, 106, 151, 2, 17, 0, 0, 0, 208, 86, 195, 102, 211, 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