Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0e5714f26e95d13f866058b38bbaff6844fe407e450a14cab288ca5210511e5

Tx prefix hash: 0e826a50d1036b8ef32c432719cc3b1f385815a239edd203f661a9bc9dd5ad45
Tx public key: 83bcfbdf3835fa61d48f9ae77ce47a6be8a1d9ad7178a2305c65280656f7aea3
Timestamp: 1713153042 Timestamp [UCT]: 2024-04-15 03:50:42 Age [y:d:h:m:s]: 00:337:16:45:00
Block: 1000770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241453 RingCT/type: yes/0
Extra: 0183bcfbdf3835fa61d48f9ae77ce47a6be8a1d9ad7178a2305c65280656f7aea30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293f30dcaea6ed739907c8ff903d894ee06e9f0cc1717672f1556d1329b0d0dc 0.600000000000 1461270 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": 1000780, "vin": [ { "gen": { "height": 1000770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293f30dcaea6ed739907c8ff903d894ee06e9f0cc1717672f1556d1329b0d0dc" } } ], "extra": [ 1, 131, 188, 251, 223, 56, 53, 250, 97, 212, 143, 154, 231, 124, 228, 122, 107, 232, 161, 217, 173, 113, 120, 162, 48, 92, 101, 40, 6, 86, 247, 174, 163, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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