Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c160bfba529fc1820cb9d9115b11793125710ca0c7a92bbf845406069bd42b

Tx prefix hash: a853ff275c479ed018d3213e1f8b6bd74461341a185c45b91cb3b10d363253f9
Tx public key: 8f3110b516c699aaf9ead726a20a6b429e7a7f80bc9fc81dbedcd1c300dcf574
Timestamp: 1740402731 Timestamp [UCT]: 2025-02-24 13:12:11 Age [y:d:h:m:s]: 00:270:01:48:44
Block: 1226235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190785 RingCT/type: yes/0
Extra: 018f3110b516c699aaf9ead726a20a6b429e7a7f80bc9fc81dbedcd1c300dcf574021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8401029a085f4084ed6b027ebadee4a1e004a144976356af0a92f7186ae3cdc4 0.600000000000 1713106 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": 1226245, "vin": [ { "gen": { "height": 1226235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8401029a085f4084ed6b027ebadee4a1e004a144976356af0a92f7186ae3cdc4" } } ], "extra": [ 1, 143, 49, 16, 181, 22, 198, 153, 170, 249, 234, 215, 38, 162, 10, 107, 66, 158, 122, 127, 128, 188, 159, 200, 29, 190, 220, 209, 195, 0, 220, 245, 116, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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