Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e595703782c62c71792cde507f369616199321563b56c2bd712617f7ba39d75

Tx prefix hash: 4665f86754d182ac2931c279080e5888f40c9d659fad83dddb7ac7c474b48b11
Tx public key: 8b0bc5ba4346d6f4ea1bcaf4caf972f194c1c45a2e29d8d7bdbbd6e586066549
Timestamp: 1729004901 Timestamp [UCT]: 2024-10-15 15:08:21 Age [y:d:h:m:s]: 00:174:22:39:59
Block: 1132217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124804 RingCT/type: yes/0
Extra: 018b0bc5ba4346d6f4ea1bcaf4caf972f194c1c45a2e29d8d7bdbbd6e58606654902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 220a923135e7122fc9ba77ed374371dfea4f59a43579c855d3c730ee00658d6a 0.600000000000 1615130 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": 1132227, "vin": [ { "gen": { "height": 1132217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "220a923135e7122fc9ba77ed374371dfea4f59a43579c855d3c730ee00658d6a" } } ], "extra": [ 1, 139, 11, 197, 186, 67, 70, 214, 244, 234, 27, 202, 244, 202, 249, 114, 241, 148, 193, 196, 90, 46, 41, 216, 215, 189, 187, 214, 229, 134, 6, 101, 73, 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