Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8434a7cc63c4e23263d3e466c9ea1ed9a4f16c17d8c75fd02c51b13f986b2906

Tx prefix hash: 971453f81216eea7181dea0291b54a0289c266a9aa04858d129b1fd69d8d02c8
Tx public key: 0722fa4d095939f0f2595c1569e0355126db9e630ac7f8610fdd500acaa43b76
Timestamp: 1712697633 Timestamp [UCT]: 2024-04-09 21:20:33 Age [y:d:h:m:s]: 00:341:05:38:28
Block: 996993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243982 RingCT/type: yes/0
Extra: 010722fa4d095939f0f2595c1569e0355126db9e630ac7f8610fdd500acaa43b76021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 790d8a5c64032481e1b3f6f7adf50b2c3e86108d0347847e035ee69a523eeab1 0.600000000000 1457421 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": 997003, "vin": [ { "gen": { "height": 996993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790d8a5c64032481e1b3f6f7adf50b2c3e86108d0347847e035ee69a523eeab1" } } ], "extra": [ 1, 7, 34, 250, 77, 9, 89, 57, 240, 242, 89, 92, 21, 105, 224, 53, 81, 38, 219, 158, 99, 10, 199, 248, 97, 15, 221, 80, 10, 202, 164, 59, 118, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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