Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9b38d591d1f2ebda387b342e39b58dfc8dcb5fbb95a965807455aa4dbcb65a7

Tx prefix hash: 550e7de977c550412bebcdc9fa1a344978c8c2c117832d1c237f7bb1ff53ef35
Tx public key: aed2d21a32410da5b21fabf1cdf8baa6aad1eb4051461019549b7cd28d3302bf
Timestamp: 1718804539 Timestamp [UCT]: 2024-06-19 13:42:19 Age [y:d:h:m:s]: 00:309:02:45:06
Block: 1047648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220899 RingCT/type: yes/0
Extra: 01aed2d21a32410da5b21fabf1cdf8baa6aad1eb4051461019549b7cd28d3302bf0211000000030bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cf3bc4cc6adc17d97a994f00ce078319a67c80654d2a13629b8a2e509ff2222 0.600000000000 1517523 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": 1047658, "vin": [ { "gen": { "height": 1047648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf3bc4cc6adc17d97a994f00ce078319a67c80654d2a13629b8a2e509ff2222" } } ], "extra": [ 1, 174, 210, 210, 26, 50, 65, 13, 165, 178, 31, 171, 241, 205, 248, 186, 166, 170, 209, 235, 64, 81, 70, 16, 25, 84, 155, 124, 210, 141, 51, 2, 191, 2, 17, 0, 0, 0, 3, 11, 186, 22, 215, 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