Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86c9d627bb8b5157c55469302cf7ba42e648a62d17826e212f090bfa6112b68

Tx prefix hash: adc7403c4b22eca70836e6083a64b8acadf2bb15b4eca09b782a12f5978bfd98
Tx public key: 01f0892a256b6c6bbbcf9e3a621446fe00ae85442c80fd0e5ba49db1aea14c6c
Timestamp: 1751274999 Timestamp [UCT]: 2025-06-30 09:16:39 Age [y:d:h:m:s]: 00:137:07:29:14
Block: 1315746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96323 RingCT/type: yes/0
Extra: 0101f0892a256b6c6bbbcf9e3a621446fe00ae85442c80fd0e5ba49db1aea14c6c0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68fb11c0dbab16401d180eb93aca52e59e79efdfd4d41a5d67449195b5415b2e 0.600000000000 1803401 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": 1315756, "vin": [ { "gen": { "height": 1315746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68fb11c0dbab16401d180eb93aca52e59e79efdfd4d41a5d67449195b5415b2e" } } ], "extra": [ 1, 1, 240, 137, 42, 37, 107, 108, 107, 187, 207, 158, 58, 98, 20, 70, 254, 0, 174, 133, 68, 44, 128, 253, 14, 91, 164, 157, 177, 174, 161, 76, 108, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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