Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15d701f31d48cd59d5072ed457834ab778038636a16a530887436c3896be1bc8

Tx prefix hash: 217cd9fc3a1a284392ab26538f97ec9f5069ee33515886f737e8fc89395b7e5b
Tx public key: fc04583c5348ae784352568c448d184f3a8f68206b21c4d428b3c56c001ec7b7
Timestamp: 1578920159 Timestamp [UCT]: 2020-01-13 12:55:59 Age [y:d:h:m:s]: 04:178:05:19:09
Block: 44620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1016778 RingCT/type: yes/0
Extra: 01fc04583c5348ae784352568c448d184f3a8f68206b21c4d428b3c56c001ec7b70211000000038a2ee0d9000000000000000000

1 output(s) for total of 436.672917957000 dcy

stealth address amount amount idx
00: c4a4ff5986226dfd0fa05065df48cc29d7103cd952e1e6a9e656765b3e3e5eb5 436.672917957000 81256 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": 44630, "vin": [ { "gen": { "height": 44620 } } ], "vout": [ { "amount": 436672917957, "target": { "key": "c4a4ff5986226dfd0fa05065df48cc29d7103cd952e1e6a9e656765b3e3e5eb5" } } ], "extra": [ 1, 252, 4, 88, 60, 83, 72, 174, 120, 67, 82, 86, 140, 68, 141, 24, 79, 58, 143, 104, 32, 107, 33, 196, 212, 40, 179, 197, 108, 0, 30, 199, 183, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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