Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b7c72044a830f5807baa93e3d98c9f8330d279abc2bbf96cf9ca55fe9deedb0

Tx prefix hash: ded4447a2bcc5eb3fcf704a16f155ee4a991fc0d8edf683fd0a259e25c4a9396
Tx public key: ca4218ff8d1fbf33bfd8fe548e2d6540558af597f4e27fd09d7583592509cd27
Timestamp: 1698394723 Timestamp [UCT]: 2023-10-27 08:18:43 Age [y:d:h:m:s]: 01:162:08:24:07
Block: 878655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377016 RingCT/type: yes/0
Extra: 01ca4218ff8d1fbf33bfd8fe548e2d6540558af597f4e27fd09d7583592509cd27021100000003faf35c9c000000000000000000

1 output(s) for total of 0.752750847000 dcy

stealth address amount amount idx
00: 9a273a86f4e677b2162430ae4cb18d3d1f780b193dc5a7ebdf19fe6b4ff4de1c 0.752750847000 1334119 of 0

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": 878665, "vin": [ { "gen": { "height": 878655 } } ], "vout": [ { "amount": 752750847, "target": { "key": "9a273a86f4e677b2162430ae4cb18d3d1f780b193dc5a7ebdf19fe6b4ff4de1c" } } ], "extra": [ 1, 202, 66, 24, 255, 141, 31, 191, 51, 191, 216, 254, 84, 142, 45, 101, 64, 85, 138, 245, 151, 244, 226, 127, 208, 157, 117, 131, 89, 37, 9, 205, 39, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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