Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15017b2c2f2454ba79f59422c3f3750e7ee490b46d2dc8c73b92ccf02bbb76f4

Tx prefix hash: 907b814b9410d51410384e3590ad16d3c517bd0c0ab4e023f21333c4d9d1387f
Tx public key: b4ca2fa70275e2c1c875fee0cef759e086f252e8fedf2b7d4b492e1de9387668
Timestamp: 1712702977 Timestamp [UCT]: 2024-04-09 22:49:37 Age [y:d:h:m:s]: 00:273:17:53:36
Block: 997039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195961 RingCT/type: yes/0
Extra: 01b4ca2fa70275e2c1c875fee0cef759e086f252e8fedf2b7d4b492e1de938766802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25d6c6ba8e9529decdeb7bd54d6d0f6dfa3431f6c36f69a32e5ee5438b7f9ca8 0.600000000000 1457467 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": 997049, "vin": [ { "gen": { "height": 997039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25d6c6ba8e9529decdeb7bd54d6d0f6dfa3431f6c36f69a32e5ee5438b7f9ca8" } } ], "extra": [ 1, 180, 202, 47, 167, 2, 117, 226, 193, 200, 117, 254, 224, 206, 247, 89, 224, 134, 242, 82, 232, 254, 223, 43, 125, 75, 73, 46, 29, 233, 56, 118, 104, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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