Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bd022a588943492da7ce50621ffd296cdeb7e9e32006f1f3ae3aa588bb30da

Tx prefix hash: fd7e26cff93171d422b70e9f44ef1c317a8811a0f6cb121c5ac78d980fada5b3
Tx public key: 50ce8fcbc27fa2c6ff8889c02318979221e2a065af7349c9fd7e457a6e9c9520
Timestamp: 1583396294 Timestamp [UCT]: 2020-03-05 08:18:14 Age [y:d:h:m:s]: 04:295:07:57:02
Block: 76630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105646 RingCT/type: yes/0
Extra: 0150ce8fcbc27fa2c6ff8889c02318979221e2a065af7349c9fd7e457a6e9c9520021100000015c71d3ff9000000000000000000

1 output(s) for total of 342.076927537000 dcy

stealth address amount amount idx
00: 88be4629b324ad66bf9306beb861a7fae555a3cd0a26438a9a853a30ce32e0b7 342.076927537000 141063 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": 76640, "vin": [ { "gen": { "height": 76630 } } ], "vout": [ { "amount": 342076927537, "target": { "key": "88be4629b324ad66bf9306beb861a7fae555a3cd0a26438a9a853a30ce32e0b7" } } ], "extra": [ 1, 80, 206, 143, 203, 194, 127, 162, 198, 255, 136, 137, 192, 35, 24, 151, 146, 33, 226, 160, 101, 175, 115, 73, 201, 253, 126, 69, 122, 110, 156, 149, 32, 2, 17, 0, 0, 0, 21, 199, 29, 63, 249, 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