Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e401a37dd07d6f610e096d10c5641f3c2608665227d1b8aa1c2d4e51861868

Tx prefix hash: 124df18cd7aa39921ba82f4755cfd2dac675fef0729de73fea1538501df14651
Tx public key: bba7d53d127baa14693fbb2519b711cf74c9d7883d9f35af860f63b4f976e015
Timestamp: 1748322235 Timestamp [UCT]: 2025-05-27 05:03:55 Age [y:d:h:m:s]: 00:174:08:11:44
Block: 1291819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122295 RingCT/type: yes/0
Extra: 01bba7d53d127baa14693fbb2519b711cf74c9d7883d9f35af860f63b4f976e01502110000000586ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce17a3e7b6cf0683608c485576198b92dbdb0e7fad74939c5949e6b2456278c 0.600000000000 1779290 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": 1291829, "vin": [ { "gen": { "height": 1291819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce17a3e7b6cf0683608c485576198b92dbdb0e7fad74939c5949e6b2456278c" } } ], "extra": [ 1, 187, 167, 213, 61, 18, 123, 170, 20, 105, 63, 187, 37, 25, 183, 17, 207, 116, 201, 215, 136, 61, 159, 53, 175, 134, 15, 99, 180, 249, 118, 224, 21, 2, 17, 0, 0, 0, 5, 134, 174, 47, 13, 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