Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f88016f371ee79e90aab23b4678c3a5f79b533c8264f41d3be8737823738e71

Tx prefix hash: bf080c9a03a4ec45e2d2e6ed2f53697a7f80d70d13f7a7f736de4a912697c466
Tx public key: 354007806d7292fbb3fbb695b1b55643dfe891a14fea30874f617f8991479c8d
Timestamp: 1720316419 Timestamp [UCT]: 2024-07-07 01:40:19 Age [y:d:h:m:s]: 00:269:01:33:53
Block: 1060174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192232 RingCT/type: yes/0
Extra: 01354007806d7292fbb3fbb695b1b55643dfe891a14fea30874f617f8991479c8d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84099a4a6fbf015dbd3f427ab1cfa6295b5db169f9c3643bfd9b822524d5920c 0.600000000000 1530645 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": 1060184, "vin": [ { "gen": { "height": 1060174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84099a4a6fbf015dbd3f427ab1cfa6295b5db169f9c3643bfd9b822524d5920c" } } ], "extra": [ 1, 53, 64, 7, 128, 109, 114, 146, 251, 179, 251, 182, 149, 177, 181, 86, 67, 223, 232, 145, 161, 79, 234, 48, 135, 79, 97, 127, 137, 145, 71, 156, 141, 2, 17, 0, 0, 0, 1, 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