Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234c41f4eb5cecc0754511379968842f3016cc53f232d7c490af0b076072bc7c

Tx prefix hash: 8012e8882534f2686f6e05b74c5b23330b1fa94a96781905caa4111c6a378016
Tx public key: 24471736aa36197930a6c6ac721cea85a27f0af4d1d12c547f5f51b4a0d87fab
Timestamp: 1712002781 Timestamp [UCT]: 2024-04-01 20:19:41 Age [y:d:h:m:s]: 01:005:05:31:58
Block: 991224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264714 RingCT/type: yes/0
Extra: 0124471736aa36197930a6c6ac721cea85a27f0af4d1d12c547f5f51b4a0d87fab02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f7895e137e6cff352f125bcf5038f0b5ad7f92a31f2d0c854a5c25c5cb6a214 0.600000000000 1451558 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": 991234, "vin": [ { "gen": { "height": 991224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7895e137e6cff352f125bcf5038f0b5ad7f92a31f2d0c854a5c25c5cb6a214" } } ], "extra": [ 1, 36, 71, 23, 54, 170, 54, 25, 121, 48, 166, 198, 172, 114, 28, 234, 133, 162, 127, 10, 244, 209, 209, 44, 84, 127, 95, 81, 180, 160, 216, 127, 171, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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