Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950501c524e54877936abbb68d5812682193484a8c6cafed4b465a0da8e3b3ff

Tx prefix hash: e9bbb94e023e92752c36114006c4589881bea80723a4488093f43d1ebe60c5e5
Tx public key: b0fb460b4538e45c0bcdc8ff7d6b3d114ab1c4c7738a26995f8b2b1774a2b89f
Timestamp: 1583931559 Timestamp [UCT]: 2020-03-11 12:59:19 Age [y:d:h:m:s]: 04:292:13:01:28
Block: 80417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104274 RingCT/type: yes/0
Extra: 01b0fb460b4538e45c0bcdc8ff7d6b3d114ab1c4c7738a26995f8b2b1774a2b89f021100000001c48ea382000000000000000000

1 output(s) for total of 332.311893974000 dcy

stealth address amount amount idx
00: c69c18d9b96ea470e1f8dbc0df389955fc203f54f18c0e9f62e06e56b6e4ce4b 332.311893974000 147193 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": 80427, "vin": [ { "gen": { "height": 80417 } } ], "vout": [ { "amount": 332311893974, "target": { "key": "c69c18d9b96ea470e1f8dbc0df389955fc203f54f18c0e9f62e06e56b6e4ce4b" } } ], "extra": [ 1, 176, 251, 70, 11, 69, 56, 228, 92, 11, 205, 200, 255, 125, 107, 61, 17, 74, 177, 196, 199, 115, 138, 38, 153, 95, 139, 43, 23, 116, 162, 184, 159, 2, 17, 0, 0, 0, 1, 196, 142, 163, 130, 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