Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b1b9f050f20bd8a55f7f36d471dc333abf146f15d8ad0da3697d3667ff8ba0

Tx prefix hash: e841dc6bf4b8e39e2b345ecc573ecf3826f76a178d8fe617704799eb94390839
Tx public key: c5f7b57bb417c617850897c4eb298a41bc0804c4aa5d4dd1d79b408945f90239
Timestamp: 1724183463 Timestamp [UCT]: 2024-08-20 19:51:03 Age [y:d:h:m:s]: 00:228:16:02:59
Block: 1092246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163289 RingCT/type: yes/0
Extra: 01c5f7b57bb417c617850897c4eb298a41bc0804c4aa5d4dd1d79b408945f9023902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b52eeb4d9b5dc5e104c494f38122d3b1538ea359e15270ad14126a2103ba159f 0.600000000000 1566953 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": 1092256, "vin": [ { "gen": { "height": 1092246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b52eeb4d9b5dc5e104c494f38122d3b1538ea359e15270ad14126a2103ba159f" } } ], "extra": [ 1, 197, 247, 181, 123, 180, 23, 198, 23, 133, 8, 151, 196, 235, 41, 138, 65, 188, 8, 4, 196, 170, 93, 77, 209, 215, 155, 64, 137, 69, 249, 2, 57, 2, 17, 0, 0, 0, 5, 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