Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f2647101d8c670b7c589a5fd13de12ec5374674f3b658eb0422fd2000bbecb

Tx prefix hash: 9420546ff35b3a0445659ba8c989b64a916aec8498487811f56ad1722a5332de
Tx public key: e7a7f3950e1ddc7aeedccc55a0417a599ff89dbfcc32f2a4edd2378a64c51efc
Timestamp: 1631791498 Timestamp [UCT]: 2021-09-16 11:24:58 Age [y:d:h:m:s]: 03:053:15:49:00
Block: 334885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 814075 RingCT/type: yes/0
Extra: 01e7a7f3950e1ddc7aeedccc55a0417a599ff89dbfcc32f2a4edd2378a64c51efc02110000000137cb3088000000000000000000

1 output(s) for total of 47.685618175000 dcy

stealth address amount amount idx
00: 1bd47c612ddb35a8ef5e7ad01fd3d3e3181b229c4eac43e0b0d124b8be534204 47.685618175000 690514 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": 334895, "vin": [ { "gen": { "height": 334885 } } ], "vout": [ { "amount": 47685618175, "target": { "key": "1bd47c612ddb35a8ef5e7ad01fd3d3e3181b229c4eac43e0b0d124b8be534204" } } ], "extra": [ 1, 231, 167, 243, 149, 14, 29, 220, 122, 238, 220, 204, 85, 160, 65, 122, 89, 159, 248, 157, 191, 204, 50, 242, 164, 237, 210, 55, 138, 100, 197, 30, 252, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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