Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a30cbb6e05e5c3630d0994718073f92d8a1536f31e03daeaa3817453b6bde4b1

Tx prefix hash: ff5c6b5ae198e947b7af1f29b57201e2f90498122a81164778e913a80ba8dcc1
Tx public key: f7d5db0a56b0fad6e9fb9a18b987723b4573f184acacca46f9f6cfd52e5301f0
Timestamp: 1577164573 Timestamp [UCT]: 2019-12-24 05:16:13 Age [y:d:h:m:s]: 05:123:14:11:27
Block: 30386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238254 RingCT/type: yes/0
Extra: 01f7d5db0a56b0fad6e9fb9a18b987723b4573f184acacca46f9f6cfd52e5301f00211000000014ac5aa02000000000000000000

1 output(s) for total of 486.765096847000 dcy

stealth address amount amount idx
00: 58b4e3be8f9b9a866a877aa479029337a707754dd31fc9b74ecd910f2ee6c555 486.765096847000 50178 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": 30396, "vin": [ { "gen": { "height": 30386 } } ], "vout": [ { "amount": 486765096847, "target": { "key": "58b4e3be8f9b9a866a877aa479029337a707754dd31fc9b74ecd910f2ee6c555" } } ], "extra": [ 1, 247, 213, 219, 10, 86, 176, 250, 214, 233, 251, 154, 24, 185, 135, 114, 59, 69, 115, 241, 132, 172, 172, 202, 70, 249, 246, 207, 213, 46, 83, 1, 240, 2, 17, 0, 0, 0, 1, 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