Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c90504811a0c7fe63f962327228923f7a8f20a87389c4d08d797e3ac98c7f89

Tx prefix hash: 6e132752915a247eea992801b52d8ecd4237f016a1393d5551c393a6aeeb5e72
Tx public key: 6f9864db3ef6696ba5cb7ca5f8d427b145bc64cb11cc66bb37545fa86c50d9b2
Timestamp: 1698504966 Timestamp [UCT]: 2023-10-28 14:56:06 Age [y:d:h:m:s]: 01:160:04:47:48
Block: 879561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375492 RingCT/type: yes/0
Extra: 016f9864db3ef6696ba5cb7ca5f8d427b145bc64cb11cc66bb37545fa86c50d9b2021100000002faf35c9c000000000000000000

1 output(s) for total of 0.747565580000 dcy

stealth address amount amount idx
00: 7d7548a8414f7ffd0fc939c70d164a930ad358dd7052e71c8a61aad3e6778009 0.747565580000 1335091 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": 879571, "vin": [ { "gen": { "height": 879561 } } ], "vout": [ { "amount": 747565580, "target": { "key": "7d7548a8414f7ffd0fc939c70d164a930ad358dd7052e71c8a61aad3e6778009" } } ], "extra": [ 1, 111, 152, 100, 219, 62, 246, 105, 107, 165, 203, 124, 165, 248, 212, 39, 177, 69, 188, 100, 203, 17, 204, 102, 187, 55, 84, 95, 168, 108, 80, 217, 178, 2, 17, 0, 0, 0, 2, 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