Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac117a72c45595e0b93fc5a3baaf6cb687f1dafb6e7315f15c8fbbbb62a09fc3

Tx prefix hash: 07be6b59bcdf597378650ebb03941040924b9af89fd687a8a416f282de971bec
Tx public key: ec77e6b46b43a851d555640b6d7309df948d4a0ec39de8edfba6709578db13a5
Timestamp: 1577825969 Timestamp [UCT]: 2019-12-31 20:59:29 Age [y:d:h:m:s]: 05:306:02:17:29
Block: 36009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366242 RingCT/type: yes/0
Extra: 01ec77e6b46b43a851d555640b6d7309df948d4a0ec39de8edfba6709578db13a50211000000044943cd9f000000000000000000

1 output(s) for total of 466.324344510000 dcy

stealth address amount amount idx
00: dea148f326254e41273953f378e25969612c7c5f93c4271ca69990b60c3e8673 466.324344510000 60841 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": 36019, "vin": [ { "gen": { "height": 36009 } } ], "vout": [ { "amount": 466324344510, "target": { "key": "dea148f326254e41273953f378e25969612c7c5f93c4271ca69990b60c3e8673" } } ], "extra": [ 1, 236, 119, 230, 180, 107, 67, 168, 81, 213, 85, 100, 11, 109, 115, 9, 223, 148, 141, 74, 14, 195, 157, 232, 237, 251, 166, 112, 149, 120, 219, 19, 165, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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