Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f24237d2f7a9bcc9cd883d3f27b590186ff7c43ebb2cceda5fc7b81f8c9056

Tx prefix hash: 46b724d7f8492922782ed86d0394b8c7964f68834caeced447e59af2239eccbf
Tx public key: 63f7d6fa46e9e7fef15194c601b500d28f6ef1b10b4184234ea51445de0b2788
Timestamp: 1732326604 Timestamp [UCT]: 2024-11-23 01:50:04 Age [y:d:h:m:s]: 00:000:20:11:15
Block: 1159656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594 RingCT/type: yes/0
Extra: 0163f7d6fa46e9e7fef15194c601b500d28f6ef1b10b4184234ea51445de0b2788021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ae68dfb31a351e41ffada4f921c0b6d434a2afb365a193a83957539358d5057 0.600000000000 1645295 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": 1159666, "vin": [ { "gen": { "height": 1159656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ae68dfb31a351e41ffada4f921c0b6d434a2afb365a193a83957539358d5057" } } ], "extra": [ 1, 99, 247, 214, 250, 70, 233, 231, 254, 241, 81, 148, 198, 1, 181, 0, 210, 143, 110, 241, 177, 11, 65, 132, 35, 78, 165, 20, 69, 222, 11, 39, 136, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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