Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0330017c2d2479a8e0363fd417a24458fb869db03bfe1bf7564431a727d8c656

Tx prefix hash: aac7154ce4e9083a5cddf6fa5059e7689bbe3c54af8a7d28a26a9b374f8470e4
Tx public key: dc07b93b400acfd3c19c86bd21edf993bd76aa468f332d1e164f485b97d0a08f
Timestamp: 1702828401 Timestamp [UCT]: 2023-12-17 15:53:21 Age [y:d:h:m:s]: 01:033:19:42:11
Block: 915191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285490 RingCT/type: yes/0
Extra: 01dc07b93b400acfd3c19c86bd21edf993bd76aa468f332d1e164f485b97d0a08f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 106d42ff5ed9691521a10acccee7b36b629eea3b0e9bd446cb443075f11473be 0.600000000000 1372579 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": 915201, "vin": [ { "gen": { "height": 915191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "106d42ff5ed9691521a10acccee7b36b629eea3b0e9bd446cb443075f11473be" } } ], "extra": [ 1, 220, 7, 185, 59, 64, 10, 207, 211, 193, 156, 134, 189, 33, 237, 249, 147, 189, 118, 170, 70, 143, 51, 45, 30, 22, 79, 72, 91, 151, 208, 160, 143, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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