Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff81ef9c355ae6ef586ff0c952eab870867d28966e6f9aba3a6d091a14f9d617

Tx prefix hash: 928945936cfb122440d475a3da77487aa481a6961d6278f60fdd0d8296422e27
Tx public key: f586046f6bfdf1425cc2bf2ae410e4c2ceba0cfc10a7d62e03dc524cb5bd0324
Timestamp: 1733284001 Timestamp [UCT]: 2024-12-04 03:46:41 Age [y:d:h:m:s]: 00:150:13:59:12
Block: 1167584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107439 RingCT/type: yes/0
Extra: 01f586046f6bfdf1425cc2bf2ae410e4c2ceba0cfc10a7d62e03dc524cb5bd03240211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03abe813687b920e7ba4eebea3b09c8599d750626a79390ec40bbfa71904560a 0.600000000000 1653281 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": 1167594, "vin": [ { "gen": { "height": 1167584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03abe813687b920e7ba4eebea3b09c8599d750626a79390ec40bbfa71904560a" } } ], "extra": [ 1, 245, 134, 4, 111, 107, 253, 241, 66, 92, 194, 191, 42, 228, 16, 228, 194, 206, 186, 12, 252, 16, 167, 214, 46, 3, 220, 82, 76, 181, 189, 3, 36, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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