Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 512ea9be4908bd79e5ea91c601395c3999ed56ee925bc64fef6340e8884eef19

Tx prefix hash: e27ca2ab52bec41ed49c4baa191149dd460e38e2308eca0e12c8555c4c513a1c
Tx public key: 75b509ff1c71f9844b29bd02023e37fab47e744e6614d705f1cf69fbc097b54f
Timestamp: 1577120356 Timestamp [UCT]: 2019-12-23 16:59:16 Age [y:d:h:m:s]: 05:043:16:10:21
Block: 30035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181067 RingCT/type: yes/0
Extra: 0175b509ff1c71f9844b29bd02023e37fab47e744e6614d705f1cf69fbc097b54f0211000000274ac5aa02000000000000000000

1 output(s) for total of 488.070365509000 dcy

stealth address amount amount idx
00: 1426a4ee63d53c0c9da9efe00a1805d99326fe3a6d9a2ec61a442f1dc69ab763 488.070365509000 49581 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": 30045, "vin": [ { "gen": { "height": 30035 } } ], "vout": [ { "amount": 488070365509, "target": { "key": "1426a4ee63d53c0c9da9efe00a1805d99326fe3a6d9a2ec61a442f1dc69ab763" } } ], "extra": [ 1, 117, 181, 9, 255, 28, 113, 249, 132, 75, 41, 189, 2, 2, 62, 55, 250, 180, 126, 116, 78, 102, 20, 215, 5, 241, 207, 105, 251, 192, 151, 181, 79, 2, 17, 0, 0, 0, 39, 74, 197, 170, 2, 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