Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76a49a91df1241dd0fe3a79aeefb73d3dc58689a9cf11859a90c9098da81376

Tx prefix hash: 103d9d79c178c10b94b3b40987e9880a6386d77a320e745406beeb5a8a386b1c
Tx public key: 0ba9ddd2b55ea1671ee8f7b76efe552991eeaa606c7e8bb165c78583da7e12ae
Timestamp: 1724374611 Timestamp [UCT]: 2024-08-23 00:56:51 Age [y:d:h:m:s]: 00:261:16:20:38
Block: 1093832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186900 RingCT/type: yes/0
Extra: 010ba9ddd2b55ea1671ee8f7b76efe552991eeaa606c7e8bb165c78583da7e12ae02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90509d5c0e5b35081ad87e3ccfed9ad88518db1f2a3bbf4f08bf7174ce40a839 0.600000000000 1568857 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": 1093842, "vin": [ { "gen": { "height": 1093832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90509d5c0e5b35081ad87e3ccfed9ad88518db1f2a3bbf4f08bf7174ce40a839" } } ], "extra": [ 1, 11, 169, 221, 210, 181, 94, 161, 103, 30, 232, 247, 183, 110, 254, 85, 41, 145, 238, 170, 96, 108, 126, 139, 177, 101, 199, 133, 131, 218, 126, 18, 174, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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