Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337ac7de2f669185507059520638704b45e94d069f36b8b4a2bd422e116c064a

Tx prefix hash: f1ac18fd17c76e68f65b3c252cec1ad6fdc31e682aa9719f5ac33090c621c403
Tx public key: 0f6cf77777f903d02ef311a897ffe9b423eb1e2aa9102be3409b715315c4e95e
Timestamp: 1582386833 Timestamp [UCT]: 2020-02-22 15:53:53 Age [y:d:h:m:s]: 04:257:16:44:35
Block: 70297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1076678 RingCT/type: yes/0
Extra: 010f6cf77777f903d02ef311a897ffe9b423eb1e2aa9102be3409b715315c4e95e021100000001724f989b000000000000000000

1 output(s) for total of 358.986122831000 dcy

stealth address amount amount idx
00: 64ca30dd0f1a25ae2da9adff0c329870fa263d1494f303e4f04c7dcb8a35e832 358.986122831000 129840 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": 70307, "vin": [ { "gen": { "height": 70297 } } ], "vout": [ { "amount": 358986122831, "target": { "key": "64ca30dd0f1a25ae2da9adff0c329870fa263d1494f303e4f04c7dcb8a35e832" } } ], "extra": [ 1, 15, 108, 247, 119, 119, 249, 3, 208, 46, 243, 17, 168, 151, 255, 233, 180, 35, 235, 30, 42, 169, 16, 43, 227, 64, 155, 113, 83, 21, 196, 233, 94, 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