Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbed92e502d2bba82f0480f25daee20620668f4652bd3daac227726f4fe1736

Tx prefix hash: 6023f30a55ebfef87c05276be3ace60a6d0a283c9cf2ada42fdcbe2b48ebcb1f
Tx public key: d77ae640bacef457b08a532b087b5c4780edbae0b4e351cfedf1b30c85a2f68f
Timestamp: 1577820902 Timestamp [UCT]: 2019-12-31 19:35:02 Age [y:d:h:m:s]: 05:064:17:38:02
Block: 35970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196009 RingCT/type: yes/0
Extra: 01d77ae640bacef457b08a532b087b5c4780edbae0b4e351cfedf1b30c85a2f68f0211000000054ac5aa02000000000000000000

1 output(s) for total of 466.476278808000 dcy

stealth address amount amount idx
00: 90e8b9cc33dc427c8d053f104053225cb8ea5cef1d852dadf4dac1a32a653453 466.476278808000 60767 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": 35980, "vin": [ { "gen": { "height": 35970 } } ], "vout": [ { "amount": 466476278808, "target": { "key": "90e8b9cc33dc427c8d053f104053225cb8ea5cef1d852dadf4dac1a32a653453" } } ], "extra": [ 1, 215, 122, 230, 64, 186, 206, 244, 87, 176, 138, 83, 43, 8, 123, 92, 71, 128, 237, 186, 224, 180, 227, 81, 207, 237, 241, 179, 12, 133, 162, 246, 143, 2, 17, 0, 0, 0, 5, 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