Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e15cde7d6e4d39299d75e28597c8afeae3041f1c22d258e981f67dda4b450715

Tx prefix hash: afa3bebb5736fe1a9b6a14e694b14b88d55569c3e77ef463baef0f8d226a0950
Tx public key: 96a8f58172951b426fbe24ea082f2211f5e6667ce56ec97990a99d1be3786cd0
Timestamp: 1731270007 Timestamp [UCT]: 2024-11-10 20:20:07 Age [y:d:h:m:s]: 00:126:15:11:25
Block: 1150905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90343 RingCT/type: yes/0
Extra: 0196a8f58172951b426fbe24ea082f2211f5e6667ce56ec97990a99d1be3786cd0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d3e52f35658a7d49ab89a58d12da1b432e04ac43bbdf9e393ca08d2f68ca6a9 0.600000000000 1636332 of 15

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": 1150915, "vin": [ { "gen": { "height": 1150905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d3e52f35658a7d49ab89a58d12da1b432e04ac43bbdf9e393ca08d2f68ca6a9" } } ], "extra": [ 1, 150, 168, 245, 129, 114, 149, 27, 66, 111, 190, 36, 234, 8, 47, 34, 17, 245, 230, 102, 124, 229, 110, 201, 121, 144, 169, 157, 27, 227, 120, 108, 208, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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