Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff669985e61ab18fe7f79b73fb6386fafb3224952f73de3e6e59f1ae09bc7201

Tx prefix hash: fc716ab274bb576c944bf6b63552ab1c0973ced1a852d0cf39d30f0a6c94b30b
Tx public key: 6feabde81f05a717a3108e0b7e09c20142d9fc5dad91e270535d29f69f7d6f79
Timestamp: 1740260838 Timestamp [UCT]: 2025-02-22 21:47:18 Age [y:d:h:m:s]: 00:228:00:57:17
Block: 1225057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160692 RingCT/type: yes/0
Extra: 016feabde81f05a717a3108e0b7e09c20142d9fc5dad91e270535d29f69f7d6f79021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4d3e5ac35a5a936e7b73b08043f9d01e475d7d1c5cbe643e2c1286d0ec325ad 0.600000000000 1711922 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": 1225067, "vin": [ { "gen": { "height": 1225057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4d3e5ac35a5a936e7b73b08043f9d01e475d7d1c5cbe643e2c1286d0ec325ad" } } ], "extra": [ 1, 111, 234, 189, 232, 31, 5, 167, 23, 163, 16, 142, 11, 126, 9, 194, 1, 66, 217, 252, 93, 173, 145, 226, 112, 83, 93, 41, 246, 159, 125, 111, 121, 2, 17, 0, 0, 0, 2, 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