Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 736fadb9e2af61a89fd04ef1ed7473391e7a60b1e176e93df88212c3b49cdb31

Tx prefix hash: b14a37cd12b7119b6e5ccc6d83335f3557aed2366cb8cdfbf40933775994d021
Tx public key: a1278fbccb7e01670a28fdb6ffc5e2e51abf8b809fea533f77984ea7abb56036
Timestamp: 1749834049 Timestamp [UCT]: 2025-06-13 17:00:49 Age [y:d:h:m:s]: 00:193:02:58:01
Block: 1304257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135825 RingCT/type: yes/0
Extra: 01a1278fbccb7e01670a28fdb6ffc5e2e51abf8b809fea533f77984ea7abb56036021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 836d59c557050ee1d007bbaf284e35c73a58341df0165224d5c2074d20316731 0.600000000000 1791844 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": 1304267, "vin": [ { "gen": { "height": 1304257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "836d59c557050ee1d007bbaf284e35c73a58341df0165224d5c2074d20316731" } } ], "extra": [ 1, 161, 39, 143, 188, 203, 126, 1, 103, 10, 40, 253, 182, 255, 197, 226, 229, 26, 191, 139, 128, 159, 234, 83, 63, 119, 152, 78, 167, 171, 181, 96, 54, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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