Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6d6f5bd27439fbd82b21dc6dc9c4f3a9ed8da52e7a4af343e1726dbe8a0e22

Tx prefix hash: 09663daba8f60e7b7324613f8fe9ba7d8fa859081e2176ba329a7fa176f6998d
Tx public key: fa5a6adef798a9e8d726ac4f43bfd452af70af4a0261cd17a9e15d75e82103e2
Timestamp: 1593017673 Timestamp [UCT]: 2020-06-24 16:54:33 Age [y:d:h:m:s]: 04:226:08:44:41
Block: 110465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101846 RingCT/type: yes/0
Extra: 01fa5a6adef798a9e8d726ac4f43bfd452af70af4a0261cd17a9e15d75e82103e202110000002746a11e8a000000000000000000

1 output(s) for total of 264.273831525000 dcy

stealth address amount amount idx
00: 2bfb86e032eaa6a89dae19e7015447a2b0e78efff4dde8773c46cc6203e80f63 264.273831525000 191349 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": 110475, "vin": [ { "gen": { "height": 110465 } } ], "vout": [ { "amount": 264273831525, "target": { "key": "2bfb86e032eaa6a89dae19e7015447a2b0e78efff4dde8773c46cc6203e80f63" } } ], "extra": [ 1, 250, 90, 106, 222, 247, 152, 169, 232, 215, 38, 172, 79, 67, 191, 212, 82, 175, 112, 175, 74, 2, 97, 205, 23, 169, 225, 93, 117, 232, 33, 3, 226, 2, 17, 0, 0, 0, 39, 70, 161, 30, 138, 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