Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0af33e75f2967b05e8d3d18d985f82ed0d38754784a7b5f7f22da29831ef67

Tx prefix hash: 71882351ae21b20d56c8e1f630524752282c131a05bed61a9c3814e2b22463cd
Tx public key: 87b93bdd090800fc4ae8a85dc5b31370b06adf75d7bcc7cbebf733cc5142d4f8
Timestamp: 1724014282 Timestamp [UCT]: 2024-08-18 20:51:22 Age [y:d:h:m:s]: 00:240:17:00:53
Block: 1090841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171908 RingCT/type: yes/0
Extra: 0187b93bdd090800fc4ae8a85dc5b31370b06adf75d7bcc7cbebf733cc5142d4f802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30432c5663ff48f70d71f865a838a1af1384b9b5cb4b1b04c31efc851403eeb2 0.600000000000 1565466 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": 1090851, "vin": [ { "gen": { "height": 1090841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30432c5663ff48f70d71f865a838a1af1384b9b5cb4b1b04c31efc851403eeb2" } } ], "extra": [ 1, 135, 185, 59, 221, 9, 8, 0, 252, 74, 232, 168, 93, 197, 179, 19, 112, 176, 106, 223, 117, 215, 188, 199, 203, 235, 247, 51, 204, 81, 66, 212, 248, 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