Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f3649b046e131e26be8647f51a943e602a0f872d9ea8b25ef79183be1dd20e

Tx prefix hash: 81b05d9fe4bd77302a3679f0cbda2bfb2c8fbbc8c41b88119ff804f1c42d1914
Tx public key: 69cad148bf7e2cc3cb8d42d6a2bae5480e6d005825eed99845abf84388e06cde
Timestamp: 1737385710 Timestamp [UCT]: 2025-01-20 15:08:30 Age [y:d:h:m:s]: 00:335:10:33:53
Block: 1201493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237345 RingCT/type: yes/0
Extra: 0169cad148bf7e2cc3cb8d42d6a2bae5480e6d005825eed99845abf84388e06cde021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cbdf1bb45d2dcc92d318e931c9b4ed641f2c8111e0a679c3830a55f667145f2 0.600000000000 1688146 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": 1201503, "vin": [ { "gen": { "height": 1201493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cbdf1bb45d2dcc92d318e931c9b4ed641f2c8111e0a679c3830a55f667145f2" } } ], "extra": [ 1, 105, 202, 209, 72, 191, 126, 44, 195, 203, 141, 66, 214, 162, 186, 229, 72, 14, 109, 0, 88, 37, 238, 217, 152, 69, 171, 248, 67, 136, 224, 108, 222, 2, 17, 0, 0, 0, 7, 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