Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fddabe64f2eb74d4d2548ceaac26356d153139f6f232e921ba0d00b666f6e3d

Tx prefix hash: caf8fa567b2c090e922a336075e74e48e5123e2c25da13ca2c70e5b0af630100
Tx public key: f4efef1f55c5e4d95c63d80670f998ee71c2dde37fd473f4ab9dd227f56e0875
Timestamp: 1721746146 Timestamp [UCT]: 2024-07-23 14:49:06 Age [y:d:h:m:s]: 01:120:11:42:00
Block: 1072026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344618 RingCT/type: yes/0
Extra: 01f4efef1f55c5e4d95c63d80670f998ee71c2dde37fd473f4ab9dd227f56e087502110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3fb62a0c595ad3080603d5de01345761fc456090e7a281e4997209a4b72a38 0.600000000000 1544453 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": 1072036, "vin": [ { "gen": { "height": 1072026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3fb62a0c595ad3080603d5de01345761fc456090e7a281e4997209a4b72a38" } } ], "extra": [ 1, 244, 239, 239, 31, 85, 197, 228, 217, 92, 99, 216, 6, 112, 249, 152, 238, 113, 194, 221, 227, 127, 212, 115, 244, 171, 157, 210, 39, 245, 110, 8, 117, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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