Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3630802249a5435c1c83341043aaabab0b2407cdc8248d4bb756a033d276fa

Tx prefix hash: 7d0f8568e1305d3b75c0157af0b6aaedaf6a03eefefb612323dc7d10ffe17cae
Tx public key: ba6db80c5f90d95adbc1f5fc6e689592a73c1df051fa7e2c2d006e335134b377
Timestamp: 1696340691 Timestamp [UCT]: 2023-10-03 13:44:51 Age [y:d:h:m:s]: 01:171:11:08:39
Block: 861607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383589 RingCT/type: yes/0
Extra: 01ba6db80c5f90d95adbc1f5fc6e689592a73c1df051fa7e2c2d006e335134b377021100000008faf35c9c000000000000000000

1 output(s) for total of 0.857310965000 dcy

stealth address amount amount idx
00: a19764314074112d8962065a835b90253e298ac4956070be2edbce92873f53c2 0.857310965000 1315961 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": 861617, "vin": [ { "gen": { "height": 861607 } } ], "vout": [ { "amount": 857310965, "target": { "key": "a19764314074112d8962065a835b90253e298ac4956070be2edbce92873f53c2" } } ], "extra": [ 1, 186, 109, 184, 12, 95, 144, 217, 90, 219, 193, 245, 252, 110, 104, 149, 146, 167, 60, 29, 240, 81, 250, 126, 44, 45, 0, 110, 51, 81, 52, 179, 119, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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