Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52e48b1850ef10cd003e31834b68f4110ecd5df67b800c8f6a45022742c20478

Tx prefix hash: 535c641e72b94de58a21dae64b78737a673e5f65ed41e24ca51193640e51a017
Tx public key: a705f83311d0b09bc9fb4a3e2e8bee7fcd91ca2c5bfad84079f1c5aeb7dbbaf7
Timestamp: 1694430313 Timestamp [UCT]: 2023-09-11 11:05:13 Age [y:d:h:m:s]: 01:237:11:46:32
Block: 845752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430850 RingCT/type: yes/0
Extra: 01a705f83311d0b09bc9fb4a3e2e8bee7fcd91ca2c5bfad84079f1c5aeb7dbbaf702110000000333af99f4000000000000000000

1 output(s) for total of 0.967548176000 dcy

stealth address amount amount idx
00: 52b0bb543d97698e523f4cd84a46a6ade3238ebdacaf439dd653f34ddc498083 0.967548176000 1299168 of 0

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": 845762, "vin": [ { "gen": { "height": 845752 } } ], "vout": [ { "amount": 967548176, "target": { "key": "52b0bb543d97698e523f4cd84a46a6ade3238ebdacaf439dd653f34ddc498083" } } ], "extra": [ 1, 167, 5, 248, 51, 17, 208, 176, 155, 201, 251, 74, 62, 46, 139, 238, 127, 205, 145, 202, 44, 91, 250, 216, 64, 121, 241, 197, 174, 183, 219, 186, 247, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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