Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd8a9424bd25e714e823bbf3854cb027ee9c70e1befa05779c171c5800b75a3

Tx prefix hash: 950dd40133a36be5a3870a07a881bc89b3cdad2a508d4a9b47b14af8c28701fc
Tx public key: ca0c2735df8e376836f413734074c6f8c6cb448acd95a371cf645e13104a8d39
Timestamp: 1725998510 Timestamp [UCT]: 2024-09-10 20:01:50 Age [y:d:h:m:s]: 00:115:15:50:07
Block: 1107290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82714 RingCT/type: yes/0
Extra: 01ca0c2735df8e376836f413734074c6f8c6cb448acd95a371cf645e13104a8d3902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8cb930c26e4bb55a652e53f12289904c781e1c8ccc40c326aece8795bf75243 0.600000000000 1584901 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": 1107300, "vin": [ { "gen": { "height": 1107290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8cb930c26e4bb55a652e53f12289904c781e1c8ccc40c326aece8795bf75243" } } ], "extra": [ 1, 202, 12, 39, 53, 223, 142, 55, 104, 54, 244, 19, 115, 64, 116, 198, 248, 198, 203, 68, 138, 205, 149, 163, 113, 207, 100, 94, 19, 16, 74, 141, 57, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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