Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 036e13ec8d5f6b16236a2d27e68f5195e818f5966d5ff8420ec0c51c01892032

Tx prefix hash: 05d7944438bd76dfd12fdd61a0ffe501bdfd2a8f224901a3642d925b305adb1c
Tx public key: ddc8c38a69f5f4d1a9aac867e9caf7f3d5883bdd1b25fd41713ac6458f9a24ae
Timestamp: 1706743249 Timestamp [UCT]: 2024-01-31 23:20:49 Age [y:d:h:m:s]: 01:084:01:52:22
Block: 947628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321185 RingCT/type: yes/0
Extra: 01ddc8c38a69f5f4d1a9aac867e9caf7f3d5883bdd1b25fd41713ac6458f9a24ae02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64e10dab93e6b7ac42a8f6d51e5369c7332ae85e3c0f462765694a94db3cb44b 0.600000000000 1405986 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": 947638, "vin": [ { "gen": { "height": 947628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64e10dab93e6b7ac42a8f6d51e5369c7332ae85e3c0f462765694a94db3cb44b" } } ], "extra": [ 1, 221, 200, 195, 138, 105, 245, 244, 209, 169, 170, 200, 103, 233, 202, 247, 243, 213, 136, 59, 221, 27, 37, 253, 65, 113, 58, 198, 69, 143, 154, 36, 174, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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